Hi @nanomad , I took the liberty to add your schedule and ICP power in #34 .... as like you I was needing the schedule parts thanks a lot! So if you want to review what I did we could merge those 2 PR.

No worries :)

Closing this one instead

As we are at it, what would be the best way to delete a schedule ?

@cliviu74 Do you want me to split ICP and Schedule as well?

You can review this indepenedtly from the time-out so that @tmenguy can then rebase his own on top of this

@cliviu74 Do you want me to split ICP and Schedule as well?

You can review this indepenedtly from the time-out so that @tmenguy can then rebase his own on top of this

Hey, good catch, didn't even noticed there's another one in there.
Yes please, we need to have separate issues for each feature, ICP and Schedule, even if they seem related.

The ICP one could be an issue as early tests on chargers that don't have an energy meter installed throw some weird errors from the Wallbox API.

@cliviu74 Split into #37

As far as I understand, we can probably feature wall this based on the product configuration API, altough I'd avoid having to call tow APIs just to update the ICP setting

Looking at the WB status endpoint, we can probably feature gate this by looking at:

• status['config_data']['icp_max_current'] not None and > 0
• 'POWER_BOOST' in status['config_data']['plan']['features']

Upon more testing, I found the following

• on installations without a power diverter, this won't do anything. The upstream wallbox API will reply with a 400 message, other than that it seems pretty benign
• I can't verify this indeed has the intended behaviour (i.e. setting ICP Max Current) so I'll take your word for it @nanomad
• As this library is intended as a simple interface to the wallbox API, I think gating should be done upstream (i.e. Home Assistant integration?!)

Based on this, I'll merge as soon as comments on the code are fixed:

• @nanomad can you please add documentation for the setIcpMaxCurrent method to README.md?

@cliviu74 README updated

Thanks to @rubens73 for the powerboost implementation

This fixes #32

Hi @nanomad, my pleasure. My username is @rubenms73, though.